System and method for synchronizing data objects in a cloud based social networking environment

ABSTRACT

Methods and systems are provided for synchronizing and sharing data objects in a cloud based social networking environment of the type including a collaboration cloud. The method includes defining a sharing configuration within the collaboration cloud to include a second computing device; running a dedicated client synchronization application on a first computing device; creating a sync folder on the first computing device using the client synchronization application; updating a data object using the first computing device; adding the updated data object to the sync folder; automatically synchronizing the updated data object with the collaboration cloud; and propagating, using the collaboration cloud, the updated data object to the second computing device.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims the benefit of U.S. provisional patentapplication Ser. No. 61/622,950 filed Apr. 11, 2012, the entire contentsof which are incorporated herein by this reference.

TECHNICAL FIELD

Embodiments of the subject matter described herein relate generally tocomputer systems and applications for synchronizing data objects and,more particularly, to a method for automatically synchronizing filesbetween a cloud-based social networking server and an associated clientapplication running on desktop and mobile computing devices.

BACKGROUND

The unprecedented growth of social technologies has redefined the waypeople connect and communicate. In social environments, on-line socialnetworks such as Facebook™, Pinterest™, Tumblr™, Google+™, Hootsuite™,and Twitter™ have forever changed the way people share information witheach other. In business environments, enterprise social networkplatforms such as Chatter™, released in June 2010 by Salesforce™ andavailable at www.salesforce.com, have revolutionized the way peoplecollaborate with each other in pursuing business opportunities. Chatterusers track projects and sales opportunities by receiving broadcastupdates about coworkers, files, and other project related data objects.Users can also form groups and post messages on each other's profiles tofacilitate collaboration.

In addition, the explosion of mobile computing technologies has drivenbusiness practices to become increasingly ubiquitous through the use ofvirtual offices leveraging tablets, laptops, and iPhone™ and Android™handsets across multiple operating systems.

At the same time, software development is evolving away from theclient-server model toward network-based processing systems that provideaccess to data and services via the Internet or other networks. Incontrast to traditional systems that host networked applications ondedicated server hardware, a “cloud” computing model allows applicationsto be provided over the network “as a service” supplied by aninfrastructure provider. The infrastructure provider typically abstractsthe underlying hardware and other resources used to deliver acustomer-developed application so that the customer no longer needs tooperate and support dedicated server hardware. The cloud computing modelcan often provide substantial cost savings to the customer over the lifeof the application because the customer no longer needs to providededicated network infrastructure, electrical and temperature controls,physical security and other logistics in support of dedicated serverhardware.

Multi-tenant cloud-based architectures have been developed to improvecollaboration, integration, and community-based cooperation betweencustomer tenants without sacrificing data security. Generally speaking,multi-tenancy refers to a system where a single hardware and softwareplatform simultaneously supports multiple user groups (also referred toas “organizations” or “tenants”) from a common data storage element(also referred to as a “multi-tenant database”). The multi-tenant designprovides a number of advantages over conventional server virtualizationsystems. First, the multi-tenant platform operator can often makeimprovements to the platform based upon collective information from theentire tenant community. Additionally, because all users in themulti-tenant environment execute applications within a common processingspace, it is relatively easy to grant or deny access to specific sets ofdata for any user within the multi-tenant platform, thereby improvingcollaboration and integration between applications and the data managedby the various applications. The multi-tenant architecture thereforeallows convenient and cost effective sharing of similar applicationfeatures between multiple sets of users.

Presently known methods for synchronizing data objects across multipleusers and/or devices include the Dropbox™ file hosting system availableat www.dropbox.com. Such systems typically involve manually updating thefile, either locally or through a web-based interface to a service cloudwhere the file is maintained, and manually uploading the updated file tothe service cloud. The updated file may then be shared with other usersand devices. However, manual file synchronization and sharing can becumbersome, time consuming, and error prone.

Systems and methods are thus needed for automatically synchronizing dataobjects with a social network service cloud, and for automatically andseamlessly sharing the updated files among pre-configured users,devices, and groups within an enterprise network.

BRIEF DESCRIPTION OF THE DRAWING FIGURES

A more complete understanding of the subject matter may be derived byreferring to the detailed description and claims when considered inconjunction with the following figures, wherein like reference numbersrefer to similar elements throughout the figures.

FIG. 1 is a schematic block diagram of a multi-tenant computingenvironment in accordance with an embodiment;

FIG. 2 is a schematic block diagram of a presently known cloud basedfile sharing scheme requiring manual uploading and synchronization ofupdated files;

FIG. 3 is a schematic block diagram of a cloud based file synchronizingand sharing scheme implementing automatic uploading and sharing ofupdated files in accordance with an embodiment;

FIG. 4 is a flow chart illustrating an exemplary method of initiallysynchronizing and sharing a data object in accordance with anembodiment;

FIG. 5 is a flow chart illustrating an exemplary method of updating andsharing a data object previously configured for automaticsynchronization in accordance with an embodiment;

FIGS. 6-10 are screen shots illustrating various aspects of an on linesocial networking environment in accordance with an embodiment;

FIG. 11 is a graphical metaphor illustrating real time seamlesssynchronizing and sharing of a data object in accordance with anembodiment;

FIG. 12 is a side-by-side comparison of various computing devicesdisplaying an exemplary on line social networking environment acrossdifferent operating systems in accordance with an embodiment;

FIG. 13 is a screen shot of an exemplary enterprise social networkingweb page using a customizable platform in accordance with an embodiment;

FIGS. 14-20 are screen shots illustrating various features of anautomatic file synchronizing and sharing application in a desk topenvironment accordance with various embodiments;

FIGS. 21-27 are screen shots illustrating various functional attributesof an automatic file synchronizing and sharing application in a mobilecomputing environment in accordance with various embodiments;

FIGS. 28-38 are screen shots illustrating various techniques for addingobjects to a file synchronizing and sharing folder in accordance withvarious embodiments; and

FIGS. 39-46 are screen shots illustrating a method for targeting a groupwhen adding content to a file synchronizing and sharing folder inaccordance with various embodiments.

DETAILED DESCRIPTION

Embodiments of the subject matter described herein generally relate tosystems and methods for automatically synchronizing updated data objects(e.g., files) with a remote service cloud, and for seamlessly sharingthe updated files in real time or near real time with a predeterminedgroup of designated users and computing devices.

The Chatter™ collaboration cloud is a web based enterprise file sharingsolution that allows users to share, collaborate on, and manage filesand other data objects with any number of authorized users or groupswithin their company or organization. The Chatterbox™ synchronizationapplication is an adjunct to the Chatter system and includes a clientapplication automatically synchronizes updated files with the cloud,thereby leveraging the pre-existing social network connections in theenterprise platform. Although the present disclosure is discussed in thecontext of Chatter and Chatterbox systems, those skilled in the art willappreciate that the techniques described herein may be implemented inany platform or computing environment which involves the synchronizationof a data object with a service cloud, and subsequent sharing of theobject with one or more enterprise devices, either directly(device-to-device) or via the cloud.

Turning now to FIG. 1, an exemplary cloud based collaboration solutionmay be implemented in the context of a multi-tenant system 100 includinga server 102 that supports applications 128 based upon data 132 from adatabase 130 that may be shared between multiple tenants, organizations,or enterprises, referred to herein as a multi-tenant database. Data andservices generated by the various applications 128 are provided via anetwork 145 to any number of client devices 140, such as desk tops,laptops, tablets, smartphones, Google Glass™, and any other computingdevice implemented in an automobile, aircraft, television, or otherbusiness or consumer electronic device or system, including web clients.

In addition to the foregoing “dedicated” syncing clients, the presentdisclosure also contemplates the automatic sharing of data and filesinto applications, such as Microsoft Word™, such that saving a documentin Word would automatically sync the document to the collaborationcloud. In an embodiment, each client device, application, or web clientis suitably configured to run a client application 142, such as theChatterbox file synchronization module or other application forperforming similar functions, as described in greater detail below.

An alternative vector into the automatic syncing and sharing may beimplemented by an application protocol interface (API), either in lieuof or in addition to the client application 142. In this way, adeveloper may create custom applications/interfaces to drive the sharingof data and/or files (and receive updates) with the same collaborationbenefits provided by the client application 142.

Each application 128 is suitably generated at run-time (or on-demand)using a common application platform 110 that securely provides access tothe data 132 in the database 130 for each of the various tenantorganizations subscribing to the service cloud 100. In accordance withone non-limiting example, the service cloud 100 is implemented in theform of an on-demand multi-tenant customer relationship management (CRM)system that can support any number of authenticated users for aplurality of tenants.

As used herein, a “tenant” or an “organization” should be understood asreferring to a group of one or more users (typically employees) thatshares access to common subset of the data within the multi-tenantdatabase 130. In this regard, each tenant includes one or more usersand/or groups associated with, authorized by, or otherwise belonging tothat respective tenant. Stated another way, each respective user withinthe multi-tenant system 100 is associated with, assigned to, orotherwise belongs to a particular one of the plurality of enterprisessupported by the system 100.

Each enterprise tenant may represent a company, corporate department,business or legal organization, and/or any other entities that maintaindata for particular sets of users (such as their respective employees orcustomers) within the multi-tenant system 100. Although multiple tenantsmay share access to the server 102 and the database 130, the particulardata and services provided from the server 102 to each tenant can besecurely isolated from those provided to other tenants. The multi-tenantarchitecture therefore allows different sets of users to sharefunctionality and hardware resources without necessarily sharing any ofthe data 132 belonging to or otherwise associated with otherorganizations.

The multi-tenant database 130 may be a repository or other data storagesystem capable of storing and managing the data 132 associated with anynumber of tenant organizations. The database 130 may be implementedusing conventional database server hardware. In various embodiments, thedatabase 130 shares processing hardware 104 with the server 102. Inother embodiments, the database 130 is implemented using separatephysical and/or virtual database server hardware that communicates withthe server 102 to perform the various functions described herein.

In an exemplary embodiment, the database 130 includes a databasemanagement system or other equivalent software capable of determining anoptimal query plan for retrieving and providing a particular subset ofthe data 132 to an instance of application (or virtual application) 128in response to a query initiated or otherwise provided by an application128, as described in greater detail below. The multi-tenant database 130may alternatively be referred to herein as an on-demand database, inthat the database 130 provides (or is available to provide) data atrun-time to on-demand virtual applications 128 generated by theapplication platform 110, as described in greater detail below.

In practice, the data 132 may be organized and formatted in any mannerto support the application platform 110. In various embodiments, thedata 132 is suitably organized into a relatively small number of largedata tables to maintain a semi-amorphous “heap”-type format. The data132 can then be organized as needed for a particular virtual application128. In various embodiments, conventional data relationships areestablished using any number of pivot tables 134 that establishindexing, uniqueness, relationships between entities, and/or otheraspects of conventional database organization as desired. Further datamanipulation and report formatting is generally performed at run-timeusing a variety of metadata constructs. Metadata within a universal datadirectory (UDD) 136, for example, can be used to describe any number offorms, reports, workflows, user access privileges, business logic andother constructs that are common to multiple tenants.

Tenant-specific formatting, functions and other constructs may bemaintained as tenant-specific metadata 138 for each tenant, as desired.Rather than forcing the data 132 into an inflexible global structurethat is common to all tenants and applications, the database 130 isorganized to be relatively amorphous, with the pivot tables 134 and themetadata 138 providing additional structure on an as-needed basis. Tothat end, the application platform 110 suitably uses the pivot tables134 and/or the metadata 138 to generate “virtual” components of thevirtual applications 128 to logically obtain, process, and present therelatively amorphous data 132 from the database 130.

The server 102 may be implemented using one or more actual and/orvirtual computing systems that collectively provide the dynamicapplication platform 110 for generating the virtual applications 128.For example, the server 102 may be implemented using a cluster of actualand/or virtual servers operating in conjunction with each other,typically in association with conventional network communications,cluster management, load balancing and other features as appropriate.The server 102 operates with any sort of conventional processinghardware 104, such as a processor 105, memory 106, input/output features107 and the like. The input/output features 107 generally represent theinterface(s) to networks (e.g., to the network 145, or any other localarea, wide area or other network), mass storage, display devices, dataentry devices and/or the like.

The processor 105 may be implemented using any suitable processingsystem, such as one or more processors, controllers, microprocessors,microcontrollers, processing cores and/or other computing resourcesspread across any number of distributed or integrated systems, includingany number of “cloud-based” or other virtual systems. The memory 106represents any non-transitory short or long term storage or othercomputer-readable media capable of storing programming instructions forexecution on the processor 105, including any sort of random accessmemory (RAM), read only memory (ROM), flash memory, magnetic or opticalmass storage, and/or the like. The computer-executable programminginstructions, when read and executed by the server 102 and/or processor105, cause the server 102 and/or processor 105 to create, generate, orotherwise facilitate the application platform 110 and/or virtualapplications 128 and perform one or more additional tasks, operations,functions, and/or processes described herein. It should be noted thatthe memory 106 represents one suitable implementation of suchcomputer-readable media, and alternatively or additionally, the server102 could receive and cooperate with external computer-readable mediathat is realized as a portable or mobile component or platform, e.g., aportable hard drive, a USB flash drive, an optical disc, or the like.

The application platform 110 is any sort of software application orother data processing engine that generates the virtual applications 128that provide data and/or services to the client devices 140. In atypical embodiment, the application platform 110 gains access toprocessing resources, communications interfaces and other features ofthe processing hardware 104 using any sort of conventional orproprietary operating system 108. The virtual applications 128 aretypically generated at run-time in response to input received from theclient devices 140. For the illustrated embodiment, the applicationplatform 110 includes a bulk data processing engine 112, a querygenerator 114, a search engine 116 that provides text indexing and othersearch functionality, and a runtime application generator 120. Each ofthese features may be implemented as a separate process or other module,and many equivalent embodiments could include different and/oradditional features, components or other modules as desired.

The runtime application generator 120 dynamically builds and executesthe virtual applications 128 in response to specific requests receivedfrom the client devices 140. The virtual applications 128 are typicallyconstructed in accordance with the tenant-specific metadata 138, whichdescribes the particular tables, reports, interfaces and/or otherfeatures of the particular application 128. In various embodiments, eachvirtual application 128 generates dynamic web content that can be servedto a browser or other client program 142 associated with its clientdevice 140, as appropriate.

The runtime application generator 120 suitably interacts with the querygenerator 114 to efficiently obtain multi-tenant data 132 from thedatabase 130 as needed in response to input queries initiated orotherwise provided by users of the client devices 140. In a typicalembodiment, the query generator 114 considers the identity of the userrequesting a particular function (along with the user's associatedtenant), and then builds and executes queries to the database 130 usingsystem-wide metadata 136, tenant specific metadata 138, pivot tables134, and/or any other available resources. The query generator 114 inthis example therefore maintains security of the common database 130 byensuring that queries are consistent with access privileges granted tothe user and/or tenant that initiated the request.

With continued reference to FIG. 1, the data processing engine 112performs bulk processing operations on the data 132 such as uploads ordownloads, updates, online transaction processing, and/or the like. Inmany embodiments, less urgent bulk processing of the data 132 can bescheduled to occur as processing resources become available, therebygiving priority to more urgent data processing by the query generator114, the search engine 116, the virtual applications 128, etc.

In exemplary embodiments, the application platform 110 is utilized tocreate and/or generate data-driven virtual applications 128 for thetenants that they support. Such virtual applications 128 may make use ofinterface features such as custom (or tenant-specific) screens 124,standard (or universal) screens 122 or the like. Any number of customand/or standard objects 126 may also be available for integration intotenant-developed virtual applications 128. As used herein, “custom”should be understood as meaning that a respective object or applicationis tenant-specific (e.g., only available to users associated with aparticular tenant in the multi-tenant system) or user-specific (e.g.,only available to a particular subset of users within the multi-tenantsystem), whereas “standard” or “universal” applications or objects areavailable across multiple tenants in the multi-tenant system.

The data 132 associated with each virtual application 128 is provided tothe database 130, as appropriate, and stored until it is requested or isotherwise needed, along with the metadata 138 that describes theparticular features (e.g., reports, tables, functions, objects, fields,formulas, code, etc.) of that particular virtual application 128. Forexample, a virtual application 128 may include a number of objects 126accessible to a tenant, wherein for each object 126 accessible to thetenant, information pertaining to its object type along with values forvarious fields associated with that respective object type aremaintained as metadata 138 in the database 130. In this regard, theobject type defines the structure (e.g., the formatting, functions andother constructs) of each respective object 126 and the various fieldsassociated therewith.

Still referring to FIG. 1, the data and services provided by the server102 can be retrieved using any sort of personal computer, mobiletelephone, tablet or other network-enabled client device 140 on thenetwork 145. In an exemplary embodiment, the client device 140 includesa display device, such as a monitor, screen, or another conventionalelectronic display capable of graphically presenting data and/orinformation retrieved from the multi-tenant database 130, as describedin greater detail below.

Typically, the user operates a conventional browser application or otherclient program 142 executed by the client device 140 to contact theserver 102 via the network 145 using a networking protocol, such as thehypertext transport protocol (HTTP) or the like. The user typicallyauthenticates his or her identity to the server 102 to obtain a sessionidentifier (“SessionID”) that identifies the user in subsequentcommunications with the server 102. When the identified user requestsaccess to a virtual application 128, the runtime application generator120 suitably creates the application at run time based upon the metadata138, as appropriate. However, if a user chooses to manually upload anupdated file (through either the web based user interface or through anAPI), it will also be shared automatically with all of the users/devicesthat are designated for sharing.

As noted above, the virtual application 128 may contain Java, ActiveX,or other content that can be presented using conventional clientsoftware running on the client device 140; other embodiments may simplyprovide dynamic web or other content that can be presented and viewed bythe user, as desired. As described in greater detail below, the querygenerator 114 suitably obtains the requested subsets of data 132 fromthe database 130 as needed to populate the tables, reports or otherfeatures of the particular virtual application 128.

In accordance with various embodiments, application 128 includes thefunctionality of a collaboration solution such as the Chatter system, aswell as the functionality of a synchronization application such as theChatterbox module. As such, application 128 is implemented at the serverto facilitate synchronization of data objects between the cloud andvarious computing devices connected to the cloud, as described in detailbelow. Specifically, application 128 allows a user to update fileslocally on the desk top, lap top, tablet, hand held, or other mobiledevice, and automatically synchronize the updated files with themulti-tenant database without having to manually upload the updatedfile. Application 128 seamlessly shares the updated files with alldesignated users and/or devices within a particular enterprise socialnetwork.

As briefly mentioned above, presently known techniques for synchronizingupdated files with a cloud based database typically require the user toopen a web browser, log onto a dedicated web portal, and thereby accessthose files stored on the multi-tenant database which the user isauthorized to access. The creation, deletion, and updating of dataobjects (files) is accomplished either locally on the device, or throughinteraction with the multi-tenant database via a web-based userinterface which may include customer relationship management (CRM) toolssuch as those available at www.salesforce.com. Once updated, the usermust upload the file to the cloud, and define the entities with whichthe file is to be shared, typically by entering a name, email address,or other identifying indicia of the entities with whom the file isdesired to be shared.

In accordance with various embodiments of the present disclosure, a dataobject synchronization application allows the user to create, delete,and revise files and automatically synchronize those files with otherusers on the enterprise social network without having to manually uploadthe updated file or separately configure file sharing.

In an embodiment, a user may install the file synchronization clientapplication 142 (e.g., Chatterbox) on any lap top, desk top, or mobilecomputing device, and identify or “register” the device within one ormore groups within the enterprise social network running on the server102. The client application 142 includes a background process whichmaintains a persistent connection (e.g., 24 hours per day and seven daysper week) between the device and the service cloud, for example via theInternet. The user may then update local versions of files, andautomatically synchronize updated versions with and receive updatedversions from the collaboration cloud without having to separatelyaccess the web-based interface.

In a further embodiment, the file synchronization application 142comprises a cross-platform application running on the desk top or mobilecomputing device for seamlessly synchronizing a user's files with acloud-based multi-tenant database. In the context of this disclosure,the term “cross-platform” implies that the synchronization engine isembodied in a single code base (i.e., application) configured tofunction across various platforms such as, for example, Windows™, Mac™,iOS™, Android™, and Linux™ operating systems.

FIG. 2 is a is a schematic block diagram of a cloud based file sharingsystem 200 which requires each updated file to be manually uploaded inorder to synchronize the file with other devices. More particularly,system 200 includes a first computing device 202 (e.g., a desk topcomputer), a second computing device 204 (e.g., a tablet computer), anda cloud based file sharing service 206.

With continued reference to FIG. 2, when a user desires to update ashared file or other data object, the file may be downloaded from thecloud along arrow 208 (if the file to be updated does not already residelocally on the device 202). The user then updates, revised, augments, orotherwise manipulates the file. The updated file is then uploaded to theservice cloud 206 along arrow 210. Typically, in order to facilitatesubsequent sharing of the updated file with other users and/or devices,the user configures and uploads sharing information along arrow 212, forexample in the form of user names, email addresses, or other suitableidentifying indicia of the users and/or devices with which or to whomthe user desires to share the updated data object.

Once the updated data object is saved in the cloud 206, an applicationrunning in the cloud 206 shares the updated file according to thesharing configuration previously uploaded (see arrow 212). For example,if device 204 is among the authorized shares, device 204 could thendownload the updated file from the cloud 206 along arrow 214. Thoseskilled in the art will appreciate that presently known synchronizingand sharing schemes typically require each updated file to be manuallyuploaded to the cloud and, in addition, the sharing details for theupdated file must also be uploaded to the cloud to permit subsequentsharing of the updated (synchronized) file. This process is cumbersome,time consuming, and error prone.

Referring now to FIG. 3, a schematic block diagram of a cloud based filesynchronizing and sharing scheme implementing automatic uploading andsharing of updated files is shown. More particularly, a first computingdevice 302 and a second computing device 304 are configured to run aclient application 328 for automatically synchronizing data objects witha service cloud 306 of the type configured to implement filesynchronization and sharing application 330, for example in the contextof one or more enterprise social networks. In an embodiment, servicecloud 306 may operate in accordance with the Chatter collaborationsolution, discussed above.

With continued reference to FIG. 3, once a data object is modified orotherwise manipulated using device 302, the synchronization application328 automatically uploads the updated object to the cloud 306, withoutrequiring additional action by the user. Once the updated object isreceived by the cloud 306, the object is seamlessly shared(synchronized) with the other authorized users and devices (includingdevice 304), in accordance with previously configured social networkingaccess controls, as described in greater detail below.

FIG. 4 is a high level flow chart illustrating an exemplary method 400for initially synchronizing and sharing a data object in accordance withan embodiment. More particularly, the method 400 includes installing(Task 402) a file synchronizing client application on a plurality ofcomputing devices. Method 400 further includes defining (Task 404) oneor more sharing configurations for a user's social network profile usingthe enterprise platform. In an embodiment, this may involve identifyingvarious devices, groups, and/or other users with whom files are to beshared.

Using a first one of the devices on which the file synchronizing clientapplication is installed, a user creates (Task 406) a new object ormodifies an existing object, either locally (i.e., off line) or via aweb based portal which connects the first device to a Chatter-typecollaboration cloud. Using a file manager application operativelyassociated with the aforementioned file synchronizing clientapplication, the updated data object is added (Task 408) to asynchronization folder, i.e., a folder used for storing files which theuser desires to synchronize with other users and/or devices, asdescribed in greater detail below in conjunction with FIGS. 6-38.

Method 400 further includes synchronizing (Task 410) the updated dataobject with the service cloud, and automatically updating (Task 412) thedata object on all shared devices.

FIG. 5 is a flow chart illustrating an exemplary method 500 ofsynchronizing and sharing a data object which was previously configuredfor automatic synchronization, for example as shown in FIG. 4. Inparticular, the method 500 includes accessing or opening (Task 502) adata object which the user desires to update, synchronize, and share.The object may be accessed locally or downloaded from the cloud via aweb based portal. The data object is then edited, updated, or otherwisemanipulated (Task 504) by the user, and then saved (Task 506),indicating that editing is complete (at least temporarily).

With continued reference to FIG. 5, method 500 further includesautomatically synchronizing (Task 508) the updated device to the cloud,and pushing (Task 510) the updates to the shared users and/or devices.

FIGS. 6-10 are exemplary screen shots illustrating various aspects of anon line social networking environment in accordance with various anembodiments. More particularly, FIG. 6 is a screen shot 600 of a profilefor a particular member 604 of an enterprise social network. The profile602 includes a feed 606, including one or more “opportunities” which, asused herein, corresponds to a sales prospect, marketing project, orother business related activity with respect to which the member 604desires to collaborate with others.

With continued reference to FIG. 6, profile 602 also includes an inviteco-workers icon 610, a recommendations section 612, a people section614, a groups section 616, a files section 618, a favorites section 620,and a search feature 622.

FIG. 7 is an exemplary screen shot 700 illustrating an expanded view ofopportunity 608. In particular, screen shot 700 illustrates a messagingfeature 702 which the user may use to send messages to co-workersregarding the status of opportunity 608.

FIG. 8 is an exemplary screen shot 800 illustrating an expanded view ofthe search feature, showing a first category 802 of search results(files) and a second category 804 of search results (groups) for thesearch term 806 (the word “competitive” in the illustrated example)entered onto a search box 808.

FIG. 9 is an exemplary screen shot 900 illustrating an expanded view ofa chat feature, showing a live conversation 904 with another userselected from a current chat menu 902.

FIG. 10 is an exemplary screen shot 1000 illustrating a detail view of aselected opportunity 1002, showing a system information section 1004 andan activity history section 1006 for the selected opportunity.

By accessing, editing, synchronizing, and sharing various data objectswithin a profile using the file synchronization and sharing techniquesdescribed herein, collaboration may be significantly enhanced. FIG. 11is a screen shot 1100 illustrating a graphical metaphor for real timeseamless synchronizing and sharing of a data object in accordance withan embodiment. More particularly, screen shot 100 depicts a data object1102 being seamlessly propagated to a second user 1106 after having beenupdated by a first user 1104 in accordance with the present disclosure.

In an embodiment, the file synchronizing and sharing techniquesdescribed herein may be implemented by any number of shared devicesacross various operating systems and device platforms. FIG. 12 is aside-by-side comparison of various computing devices displaying anexemplary on line social networking environment across differentoperating systems. In particular, FIG. 12 shows a smartphone 1202, adesk top computer 1204, and a tablet computer 1206 each displaying arespective version of the social networking environment optimized forthe device. By coordinating the enterprise social networking environmentacross various computing device this way, synchronized data objects maybe seamlessly accessed by different devices using familiar navigationalfeatures, as described in greater detail below.

Moreover, by providing a customizable user interface platform for filesynchronizing and sharing within an enterprise, each organization(tenant) may utilize the features described herein while maintaining aconsistent corporate identity. By way of non-limiting example, FIG. 13is a screen shot 1300 of an exemplary enterprise social networking webpage 1302 using a customizable platform in accordance with anembodiment. Web page 1302 may be customized to include a company logo1304, organization specific files, applications, and features 1306, anda desired color scheme 1308.

FIGS. 14-20 are screen shots illustrating various features of anautomatic file synchronizing and sharing application in a desk topenvironment in accordance with various embodiments.

More particularly, FIG. 14 is a screen shot 1400 illustrating a Macoperating system look and feel for a desk top version implementation ofa file synchronizing and sharing application. In particular, screen shot1400 includes a Chatterbox icon 1402 in a system tray 1404, a Chatterboxfolder 1406 in a favorites menu 1408, a Chatterbox navigation icon 1410disposed near the top center of the desk top, and a cloud icon

FIG. 15 is a screen shot 1500 of the desk top of FIG. 14, expanding andhighlighting various Chatterbox features. Specifically, a Chatterboxcloud icon 1502 is shown with an associated drop down menu 1503 forcommunicating status, storage, and preferences information. Screen shot1500 also includes a Chatterbox filter 1506 in the finder favorites bar1508.

FIG. 16 is a screen shot 1600 showing the contents 1602 of documentsfolder overlaid on the desk top of FIG. 14. In an embodiment, a file orother data object may be added to the Chatterbox folder 1604 by draggingand dropping, right clicking the file and selecting the “Chatterbox”folder, or in any other convenient fashion. For example, FIG. 17 shows ascreen shot 1700 illustrating a technique for highlighting a group offiles and dragging them into the Chatterbox folder using native filesystem interaction.

FIG. 18 is a screen shot 1800 illustrating the syncing of files to theuser in two ways: i) by using an animated Chatterbox icon 1802 in themenu bar; and ii) by overlaying a syncing icon 1804 at the file levelfor each file being synced.

FIG. 19 is a screen shot 1900 displaying status overlay icons 1902having check marks, indicating that the files have updated(synchronized) in the cloud.

FIG. 20 is a screen shot 2000 illustrating the local file system (thedesk top environment) 2002 showing the Chatterbox files 2004, mirroredagainst the Chatter (web browser) view 2006 of the files list 2008. Notethat after syncing is complete, both the local and the web based viewsof the Chatterbox folder contain the same list of files.

In accordance with an embodiment, notifications may be used to let usersknow that data/files have been synchronized. Because files areautomatically synchronized, it will not always be clear that a file haschanged, particularly in the case where the data/file is shared withothers. Therefore, notifications may be employed across all platforms,including mobile, desktop, and web clients. These notifications advisethe user that there has been an update and guide the user to the changeddata/file. Notifications can also be accessed through an API toautomatically drive external applications. Moreover, while one exampleof syncing surrounds the addition of a new file, other activities canalso trigger an automatic update, for example the deletion ormodification of data/files, or a change to metadata such as a timestampchange, the addition of notes, or the like.

Automatic synchronizing and sharing can also be integrated with a widerange of functionality including business processes, email, and externalsystems. Business process integration involves integrating the syncingfunction with work flows, approvals, tasks, and any other businessprocess metric. Email integration may involve syncing/sharing throughemail, and automatically syncing/sharing when an email attachment isreplaced, updated, or otherwise manipulated. External system integrationinvolves syncing/sharing when a file or data is added to an externalrepository, such as the Documentum store.

FIGS. 21-27 are screen shots illustrating various functional attributesof an automatic file synchronizing and sharing application in a mobilecomputing environment in accordance with various embodiments. Moreparticularly, FIG. 21 is a screen shot 2100 showing an iOS userinterface on an iPhone 201 juxtaposed with a mobile user interface on atablet 2104. Each device is displaying a “push” notification associatedwith an event related to the aforementioned Chatterbox functionality. Itshould be noted that clicking on the notification takes the userdirectly to the list of files, and highlights the changed files.

In addition to the desk top environment discussed above in connectionwith FIGS. 14-20, there are a number of other ways in which files can beadded to the Chatterbox folder from the web based portal, mobiledevices, and from the broader Chatter environment, as will now bediscussed.

FIG. 22 is a screen shot 2200 of an iPad user interface, showing anemail folder 2202 on the left and a selected email 2204 on the rightincluding a Powerpoint™ presentation 2206 as an attachment. FIG. 23 is ascreen shot 2300 showing a long press 2302 on the attachment 2206 toreveal context specific options.

More particularly, FIG. 24 is a screen shot 2400 illustrating a menu2402 including an “Add to Chatterbox” option 2406. FIG. 25 is a screenshot 2500 illustrating the user selecting 2502 the “Add to Chatterbox”option 2406 which, when selected by the user, adds the presentationattachment 2206 to the Chatterbox folder. In the illustrated example,once the object is added to the Chatterbox folder, the applicationswitches to the Chatter view 2602 shown in FIG. 26. FIG. 27 is a screenshot 2700 illustrating the Chatter view of the files 2702 currently inthe Chatterbox folder, with the most recently added file 2704highlighted.

FIGS. 28-38 are screen shots illustrating various techniques for addingobjects to a file synchronizing and sharing folder from other sources inaccordance with various embodiments. In particular, FIG. 28 is a screenshot 2800 illustrating an exemplary feed 2802 within the profile of auser 2804. Specifically, a colleague 2806 has posted a file 2808 pickedup by the feed 2802, and the user 2804 desires to save the file and makeit available across the user's other devices. Accordingly, the userpresses 2808 the “add to Chatterbox” option 2810, thereby adding thefile 2808 to the Chatterbox folder directly from the feed post. Withmomentary reference to FIG. 29, a screen shot 2900 shows a desk topnotification 2902 indicating that the file was added to the Chatterboxfolder. In addition, the status indicator “In Chatterbox” 2904 alsoconfirms that the file entitled “Conference Pricing” was added to theChatterbox folder.

FIG. 30 is a screen shot 3000 showing a view from the web based Chatterenvironment including a list 3002 of files contained within a particularuser's 3006 Chatter profile. A status column 3004 indicated which filesare in, and which files are not in, the Chatterbox folder. Specifically,those files having a solid circle 3008 next to the file name (column3004) are already in the Chatterbox folder; those files marked with anopen circle 3010 are not in the Chatterbox folder. This allows the userto quickly determine at a glance which files the user may wish to add tothe Chatterbox folder.

FIG. 31 is a screen shot 3100 of the Chatter environment showing theuser hovering 3102 over a particular file 3106, thereby revealing a tooltip 3104 (“Add this file to Chatterbox”). Clicking on the tool tip 3104adds the corresponding file to the Chatterbox folder.

Referring now to FIGS. 32-38, various techniques for adding a “group”object to the Chatterbox folder in accordance with various embodimentswill now be described.

FIG. 32 is a screen shot 3200 of a Chatter view web page, showing emailoptions 3202 including an “Add this Group to Chatterbox” option 3204. Byclicking 3206 this option, the entire folder associated with the “SalesTeam” group may be added to the Chatterbox folder. In this regard, FIG.33 is a screen shot 3300 showing a notification icon 3302 confirmingthat the “Sales Team” group folder was added to the Chatterbox folder.The files 3304 within the Sales Team group folder are shown at the lowerright hand corner of screen shot 3300.

Referring now to FIG. 34, a screen shot 3400 illustrates that, after agroup is added to the Chatterbox folder, that group folder 3402 appearsin the root 3404 of the Chatterbox folder 3406. With reference to FIGS.34 and 35, clicking on the groups folder 3402 reveals a list 3502 offolder which includes the groups added to the Chatterbox folder(including the Sales Team group folder 3504), as seen in the screen shot3500 shown in FIG. 35.

With reference to FIGS. 35 and 36, clicking on the Sales Team groupfolder 3504 reveals the files 3602 located in that folder, as shown inthe screen shot 3600 shown in FIG. 36.

FIG. 37 is a screen shot 3700 showing the desk top OS view 3702representing the same file hierarchy 3704 depicted in the previousChatter environment; namely a groups folder 3706, a Sales Team groupfolder 3710 within the groups folder 3706, and the Sales Team files 3712contained within the Sales Team group folder 3710.

FIG. 38 is a screen shot 3800 illustrating an analogous file hierarchyin a tablet environment. In particular, screen shot 3800 shows aChatterbox folder 3802 which includes a groups folder 3804. Within thegroups folder 3804 are a number groups 3806, including the Sales Teamgroup folder 3808.

In accordance with various embodiments, data and files can beautomatically shared with specified groups, chatter groups (includingthose with external customers), all of a user's social networkingcontacts, or no one. The latter case (no one) is considered a defaultposition, and can simply back up data and files to the cloud or to auser's other devices. It is also contemplated that data and files can beshared based on defined criteria or metadata associated with thedata/files being synchronized/shared. For example, if the metadataindicates that a particular file contains “HR documentation”, the filecan be automatically saved shared with HR-related groups, personnel, andthe like, as desired.

Moreover, data synchronization/sharing may initiated when data (asopposed to a file) is updated. By way of non-limiting example, anautomobile computer can be configured to automatically synchronize andshare an updated data object when scheduled maintenance is due to beperformed, and thereby cause a notification to the user's tablet, mobilephone, and the like.

FIGS. 39-46 are screen shots illustrating a method for targeting a groupwhen adding content to a file synchronizing and sharing folder inaccordance with various embodiments.

More particularly, FIG. 39 is a screen shot 3900 of an iPad OS view of ablog 3902 in a web browser, including a link 3904 to a PDF version of anarticle. FIG. 40 is a screen shot 4000 of a long press 4002 on the link3904, which reveals a contextual menu 4102, as shown in a screen shot4100 (FIG. 41). FIG. 42 is a screen shot 4200 showing the user clickingon the “Add to a Chatter Group” option 4204 from the menu 4102 tothereby add the PDF link to a Chatter group. Clicking option 4204 alsoswitches the user from the browser to the Chatter view, as depicted inthe side-by-side comparison of the browser view 4302 (showing the blog3902) AND THE Chatter view 4304.

Referring now to FIG. 44, a screen shot 4400 shows, in the Chatter view,a file sharing page 4402 including a list 4404 of groups the userbelongs to. The user selects the desired group 4408 from the list byclicking on it 4406. Referring now to FIG. 45, a screen shot 4500confirms that the Sales Team group 4502 was selected by placing a checkmark 4504 next to that group. Screen shot 4500 also illustrates a notepad presented to the user, prompting the user to write a note (ifdesired) to be attached to the shared file.

FIG. 47 is a screen shot 4600 showing the feed 4602 of the Sales Teamgroup, including the linked article 4604. Screen shot 4600 also includesa notification 4606 confirming that the Sales Team group has been addedto the Chatterbox folder.

It can thus be seen that in the context of the present disclosure, adata object can include a file such as a word processing document, photoalbum, video, song, Powerpoint or other presentation type, slide show,opportunity, group, data record (name, title, email address, postaladdress), or virtually any other type of content and/or informationobject.

A computer implemented application is thus provided for automaticallysynchronizing data objects between a local computing device and a remotemulti-tenant database, and for automatically and seamlessly propagatingthe updated data object across other devices and users.

A method is provided for synchronizing and sharing data objects in acloud based social networking environment of the type including acollaboration cloud. The method includes defining a sharingconfiguration within the collaboration cloud which includes a secondcomputing device; running a dedicated client synchronization applicationon a first computing device; creating a sync folder on the firstcomputing device using the client synchronization application; updatinga data object using the first computing device; adding the updated dataobject to the sync folder; automatically synchronizing the updated dataobject with the collaboration cloud; and propagating, using thecollaboration cloud, the updated data object to the second computingdevice.

In an embodiment, the step of defining involves defining a sharingconfiguration which also includes a plurality of additional computingdevices, and the step of propagating further comprises propagating theupdated data object to the plurality of additional computing devices.

In a further embodiment, the data object may consist of a text file,photo album, video, song, presentation, slide show, opportunity, group,or a data record. Moreover, the second computing device may include adesk top, laptop, tablet, smartphone, or a Google Glass™ device.

In a further embodiment, the second computing device is implemented inone of: an automobile, an aircraft, a television, and a hand heldelectronic device.

In another embodiment, defining involves configuring social networkingaffiliations.

In yet a further embodiment, the client synchronization application isconfigured to automatically synchronize the updated data object with thecollaboration cloud upon saving the updated data object to the firstcomputing device, and the client synchronization application isconfigured to automatically create the sync folder upon installing theclient synchronization application on the first computing device.

In another embodiment, updating involves one of creating, revising,augmenting, deleting, and changing metadata associated with at least aportion of the data object.

In another embodiment, adding comprises manually moving the updated dataobject to the sync folder, for example, by dragging and dropping thedata object into the sync folder.

In a further embodiment, propagating involves propagating the updateddata object to at least one of the plurality of additional computingdevices via email.

In another embodiment, the dedicated client synchronization applicationis or includes an application protocol interface (API).

In yet another embodiment, defining a sharing configuration is based onat least one metadata key word.

In a further embodiment, the method may involve sending a notificationto the second computing that the data object has been an updated.

A method is also provided for synchronizing and sharing a data objectbetween a first computing device and a plurality of collaboratingcomputing devices using a cloud-based social networking server. Themethod includes: installing a client application on the first computingdevice and the collaborating computing devices; creating a sync folderon the first computing device using the client application; updating thedata object; saving the data object to the first computing device; inresponse to saving, automatically synchronizing the updated data objectwith the server using the client application; and automatically pushingthe updated data object to each of the plurality of collaboratingcomputing devices.

In an embodiment, pushing involves at least one of: i) transmitting theupdated data object; and ii) transmitting a notification that the dataobject has been updated. In another embodiment, pushing involves atleast one of: i) sending the updated data object from the server to atleast one of the plurality of collaborating computing devices; and ii)sending the updated data object from the first computing device to atleast one of the plurality of collaborating computing devices via email.

In a further embodiment, the data object comprises one of: a text file,photo album, video, song, presentation, slide show, opportunity, group,and data record; the second computing device comprises one of a: desktop, laptop, tablet, smartphone, and Google Glass™; and updatingcomprises one of creating, revising, augmenting, deleting, and changingmetadata associated with the data object.

A computer application is also provided. The application may be embodiedin a non-transitory medium for operation by a computer processorassociated with a social networking server, and configured to performthe steps of: defining a sharing configuration including a plurality ofcollaborating computing devices; receiving an updated data object from aclient syncing application running on a first computing device; andautomatically sharing the updated data object with the plurality ofcomputing devices.

The foregoing description is merely illustrative in nature and is notintended to limit the embodiments of the subject matter or theapplication and uses of such embodiments. Furthermore, there is nointention to be bound by any expressed or implied theory presented inthe technical field, background, or the detailed description. As usedherein, the word “exemplary” means “serving as an example, instance, orillustration.” Any implementation described herein as exemplary is notnecessarily to be construed as preferred or advantageous over otherimplementations, and the exemplary embodiments described herein are notintended to limit the scope or applicability of the subject matter inany way.

For the sake of brevity, conventional techniques related to computerprogramming, computer networking, database querying, databasestatistics, query plan generation, XML and other functional aspects ofthe systems (and the individual operating components of the systems) maynot be described in detail herein. In addition, those skilled in the artwill appreciate that embodiments may be practiced in conjunction withany number of system and/or network architectures, data transmissionprotocols, and device configurations, and that the system describedherein is merely one suitable example. Furthermore, certain terminologymay be used herein for the purpose of reference only, and thus is notintended to be limiting. For example, the terms “first”, “second” andother such numerical terms do not imply a sequence or order unlessclearly indicated by the context.

Embodiments of the subject matter may be described herein in terms offunctional and/or logical block components, and with reference tosymbolic representations of operations, processing tasks, and functionsthat may be performed by various computing components or devices. Suchoperations, tasks, and functions are sometimes referred to as beingcomputer-executed, computerized, software-implemented, orcomputer-implemented. In this regard, it should be appreciated that thevarious block components shown in the figures may be realized by anynumber of hardware, software, and/or firmware components configured toperform the specified functions.

For example, an embodiment of a system or a component may employ variousintegrated circuit components, e.g., memory elements, digital signalprocessing elements, logic elements, look-up tables, or the like, whichmay carry out a variety of functions under the control of one or moremicroprocessors or other control devices. In this regard, the subjectmatter described herein can be implemented in the context of anycomputer-implemented system and/or in connection with two or moreseparate and distinct computer-implemented systems that cooperate andcommunicate with one another. That said, in exemplary embodiments, thesubject matter described herein is implemented in conjunction with avirtual customer relationship management (CRM) application in amulti-tenant environment.

While at least one exemplary embodiment has been presented in theforegoing detailed description, it should be appreciated that a vastnumber of variations exist. It should also be appreciated that theexemplary embodiment or embodiments described herein are not intended tolimit the scope, applicability, or configuration of the claimed subjectmatter in any way. Rather, the foregoing detailed description willprovide those skilled in the art with a convenient road map forimplementing the described embodiment or embodiments. It should beunderstood that various changes can be made in the function andarrangement of elements without departing from the scope defined by theclaims, which includes known equivalents and foreseeable equivalents atthe time of filing this patent application. Accordingly, details of theexemplary embodiments or other limitations described above should not beread into the claims absent a clear intention to the contrary.

What is claimed:
 1. A method of synchronizing and sharing data objectsin a cloud based social networking environment of the type including acollaboration cloud, the method comprising: configuring socialnetworking affiliations to define a sharing configuration, within thecollaboration cloud, the sharing configuration including a secondcomputing device; running a dedicated client synchronization applicationon a first computing device; creating a sync folder on the firstcomputing device using the client synchronization application; updatinga data object using the first computing device; adding the updated dataobject to the sync folder; in response to updating the data object,automatically synchronizing the updated data object with thecollaboration cloud without requiring additional user action at thefirst computing device; and propagating, using the collaboration cloud,the updated data object to the second computing device.
 2. The method ofclaim 1, wherein: defining comprises defining a sharing configurationwhich further includes a plurality of additional computing devices; andpropagating further comprises propagating the updated data object to theplurality of additional computing devices.
 3. The method of claim 2,wherein propagating comprises propagating the updated data object to atleast one of the plurality of additional computing devices via email. 4.The method of claim 1, wherein the data object comprises one of: a textfile, photo album, video, song, presentation, slide show, opportunity,group, and data record.
 5. The method of claim 1, wherein the secondcomputing device comprises one of a: desktop, laptop, tablet,smartphone, and Google Glass™.
 6. The method of claim 1, wherein thesecond computing device is implemented in one of: an automobile, anaircraft, a television, and a hand held electronic device.
 7. The methodof claim 1, wherein the client synchronization application is configuredto automatically synchronize the updated data object with thecollaboration cloud upon saving the updated data object to the firstcomputing device.
 8. The method of claim 1, wherein the clientsynchronization application is configured to automatically create thesync folder upon installing the client synchronization application onthe first computing device.
 9. The method of claim 1, wherein updatingcomprises one of creating, revising, augmenting, deleting, and changingmetadata associated with at least a portion of the data object.
 10. Themethod of claim 1, wherein adding comprises manually moving the updateddata object to the sync folder.
 11. The method of claim 10, whereinmanually comprises dragging and dropping the data object into the syncfolder.
 12. The method of claim 1, wherein the dedicated clientsynchronization application comprises an application protocol interface(API).
 13. The method of claim 1, wherein defining a sharingconfiguration is based on at least one metadata key word.
 14. The methodof claim 1, further comprising sending a notification to the secondcomputing that the data object has been an updated.
 15. A method forsynchronizing and sharing a data object between a first computing deviceand a plurality of collaborating computing devices using a cloud-basedsocial networking server, comprising: installing a client application onthe first computing device and the collaborating computing devices;configuring social networking affiliations via the first computingdevice to define a sharing configuration, within the collaborationcloud, the sharing configuration including the collaborating computingdevices; creating a sync folder on the first computing device using theclient application; updating the data object; saving the data object tothe first computing device; in response to saving, automaticallysynchronizing the updated data object with the server using the clientapplication without requiring additional user action at the firstcomputing device; and automatically pushing the updated data object toeach of the plurality of collaborating computing devices.
 16. The methodof claim 15, wherein pushing comprises at least one of: i) transmittingthe updated data object; and ii) transmitting a notification that thedata object has been updated.
 17. The method of claim 15, whereinpushing comprises at least one of: i) sending the updated data objectfrom the server to at least one of the plurality of collaboratingcomputing devices; and ii) sending the updated data object from thefirst computing device to at least one of the plurality of collaboratingcomputing devices via email.
 18. The method of claim 15, wherein: thedata object comprises one of: a text file, photo album, video, song,presentation, slide show, opportunity, group, and data record; thesecond computing device comprises one of a: desk top, laptop, tablet,smartphone, and Google Glass™; and updating comprises one of creating,revising, augmenting, deleting, and changing metadata associated withthe data object.
 19. A computer application embodied in a non-transitorymedium for operation by a computer processor associated with a socialnetworking server for performing the steps of: configuring socialnetworking affiliations to define a sharing configuration including afirst computing device and a plurality of other collaborating computingdevices; receiving, from a client syncing application running on thefirst computing device when a data object is updated at the firstcomputing device, an updated data object to automatically synchronizethe updated data object at the social networking server, wherein theupdated data object is automatically communicated to the socialnetworking server by the client syncing application when the data objectis updated at the first computing device without requiring additionaluser action at the first computing device; and automatically sharing theupdated data object with the plurality of other collaborating computingdevices.